AKern Security Guidelines Document 1
the AKern codebase System for Testing and Development

NOTE BEFORE READING:
    Testing your own code can seem to be a tedious task, however,
   with these steps in mind it can be much easier and more efficient.
    This document is made to provide a guideline on testing,
   so that your code is safe and stable for users, and easier
   to maintain by developers.

------

Before beginning development on a new feature or improving
    an existing one, be sure to test the way you plan to
    use existing features for this one.
This does not apply for uses that have already been tested.

That way, bugs could be solved before a new feature or
    improvement is added.

Once all tests are working as expected, development on a
    new feature can begin.

After developing an improvement or feature, try testing as
    many intended uses as you can.

------

Regularly, code should be checked for any possible errors.
If you think an error is somewhere, test the function in
    a way that would cause it to occur.
If the result is what is expected for that use, this can
    be ignored.

------

Before programming, think through the logic of what you are doing.
Divide each task you are implementing into it's individual steps.

This will save the stress of not knowing what your code is really
    doing.
